Oracle PeopleSoft Enterprise Management Configuration Configure GL accounts, single vendor, and other information in Oracle PeopleSoft Enterprise Management AP Request Integration Point Configure an AP Business Unit in Oracle PeopleSoft Enterprise Management (Optional) If you plan to send Oracle Utilities Customer Care and Billing data to an existing AP business unit, your existing Oracle PeopleSoft Enterprise Management configuration will suffice. If you need to segregate Oracle Utilities Customer Care and Billing data by AP business unit from other data within Oracle PeopleSoft Enterprise Management , create a new AP Business Unit definition. Take note of the AP Business Unit being used, as you will need this in subsequent steps. Identify the Accounting Entry Template If you already have a Accounting Entry Template defined to offset incoming Oracle Utilities Customer Care and Billing Accounts then you do not need to setup a new one. You should however document in the implementation checklist the name of this Accounting Entry Template as it is used to accommodate the accounts that accompany the vouchers coming from Oracle Utilities Customer Care and Billing and you will need it in subsequent implementation steps. Configure the Single Payment Vendor in Oracle PeopleSoft Enterprise Management You must set up a Single Payment Vendor in Oracle PeopleSoft Enterprise Management to represent default accounting information for all of the incoming AP Requests from Oracle Utilities Customer Care and Billing. To do this you will also need to know the name of the Accounting Entry template in Oracle PeopleSoft Enterprise Management to offset incoming Oracle Utilities Customer Care and Billing Accounts. The field values described below in the table are minimum setup values required to setup a single Payment vendor. Based on the client requirements values for other fields may or may not be required. To Configure the Single Payment Vendor in Oracle PeopleSoft Enterprise Management: 1. Open Oracle PeopleSoft Enterprise Management Financials and Navigate to Vendors Page Vendors > Vendor Information > Add/Update > Vendor. 2. Create Single Payment Vendor by Selecting the Add a New Value tab. Choose the Single Payment Vendor (SGLP) persistence. 3. Use the following settings: Field Label Value Comments SetID SHARE VENDOR CCBVENDOR This is an example value. You may use any value you wish but take note of it for future configuration steps. ShortName CCBVENDOR Example Name CCB Single Payment Vendor Example Description CCB Single Payment Vendor Example Terms Options Default This field denotes the payment terms of the voucher. It will have 2 possible values: 1. Default: Values defaulted from higher level setup. 2. Specify: Terms must be specified in the Terms field. Currency options Default This field denotes the currency code specification. Two possible values are: 1. Default: Values defaulted from higher level setup. 2. Specify: Terms must be specified in the Terms field. Handling Options Default This field denotes Payment Handling options for individual payments of this vendor. Two possible values are: 1. Default: Values defaulted from higher level setup 2. Specify: Terms must be specified in the Terms field. Banking Options Default This field denotes the Banking options for this vendor. Two possible values are: 1. Default: Values defaulted from higher level setup. 2. Specify: Terms must be specified in the Terms field. Configure the Payment Terms Code in Oracle PeopleSoft Enterprise Management To Configure the Payment Terms Code in Oracle PeopleSoft Enterprise Management follow these steps: 1. Open Oracle PeopleSoft Enterprise Management Financials and navigate to the Procurement Options Payment Terms Timing Codes tab. Set Up Financials/Supply Chain > Product Related > Procurement Options > Payments > Payment Terms Timing Codes 2. Create a Payment Terms Timing Code by selecting the Add a New Value tab SetID: Share Timing Definition ID: 07 (example) 3. Define additional timing code values on the Payment Terms Timing Codes screen. Field Label Value Comments SetID SHARE SetID Timing ID 07 Timing Definition ID Description 7 Days Description Short Description 7 Days Short Description Timing Basis Option None End of Relative Month Fixed Month Day Values Specific Due Date Timing Basis Option Timing Adjustment Day Increment Month Increment Year Increment Timing Adjustment In this example the Days Increment is set to "7" to indicate that the amount will be paid seven days after the Invoice date. 4. Create a Payment Terms Code using the Payment Terms Timing Code that was created. Set Up Financials/Supply Chain > Product Related > Procurement Options > Payments > Payment Terms-Single Payment 5. Create a Payment Terms - Single Payment Code by selecting the Add a New Value tab. SetID: Share Timing Definition ID: 07 (example) 6. Select the desired Payment Terms Timing code in the Timing ID field to complete the creation of the Payment Terms Code. Field Label Value Comments SetID SHARE SetID Description CCB Refund Payment Terms code Description Payment Terms ID 07 Payment Terms ID Short Description CCBREFUND Short Description Effective Date 01/01/1900 Effective Date Terms Applicability Vendor-Only Terms Terms Applicability Status Active Effective Status Split Net Terms No Split Net Terms Basis From and To Days 01 and 31 Only apply when Starting and Ending Day of the month Timing ID 07 Net Terms Timing ID Rebate Term Available No Rebate Term Available Daily Rebate Percent 0 Daily Rebate Percent Maximum Rebate 0 Maximum Rebate Percent Discount Terms Available No Discount Terms Available Discount Terms No Discount Terms AP Data Integration Point No configuration is required in Oracle PeopleSoft Enterprise Management for this integration point. Product delivered application tables are used for selecting data from Oracle PeopleSoft Enterprise Management to export payment information to Oracle Utilities Customer Care and Billing.